Test case consolidator

ABSTRACT

A method for consolidating DDT spreadsheets is provided. The spreadsheets may be for testing with a test executable program. Methods may store a plurality of DDT spreadsheets in a collective DDT folder. Methods may create a single collective spreadsheet. Methods may store the single collective spreadsheet in the collective DDT folder. Methods may identify a plurality of empty cells within each DDT spreadsheet. Methods may enter a filler entry into each cell determined to be empty. Methods may copy each sheet that includes at least one test executable into the single collective spreadsheet. Methods may process each test executable included in the single collective spreadsheet. Methods may place the results of each test executable in a column orthogonal to the test executable row. Methods may copy each test executable and the results of each test executable into the plurality of DDT spreadsheets from which the test executable were copied.

FIELD OF TECHNOLOGY

This invention relates to consolidation. More specifically, thisinvention relates to consolidation of test executables.

BACKGROUND OF THE DISCLOSURE

Transactions are typically entered into spreadsheets. The spreadsheetsare then transmitted to a processor. The processor may process thetransactions. Processing spreadsheets may involve certain technicaldifficulties. One specific technical difficulty associated withprocessing spreadsheets may involve processing speeds. Conventionally, aprocessor may only be capable of processing one spreadsheet at a time.Therefore, processing multiple transactions included in multiplespreadsheets may waste time and waste human effort. Because thespreadsheets must be processed in serial by a single processor, removinga processed spreadsheet from the processor and placing a new spreadsheetinto the processor may be particularly time-consuming. Therefore, it maybe desirable to consolidate the spreadsheets into one spreadsheet inorder to process the transactions in an aggregated manner.

SUMMARY OF THE DISCLOSURE

A method for consolidating test executables is provided. Theconsolidation may conserve computing resources. The conservation ofcomputing resources may occur during processing of the test executableswithin a testing framework. The method may include receiving a pluralityof original spreadsheets. Each original spreadsheet may include at leastone sheet. Each row included in the at least one sheet may include atest executable.

The method may include determining a plurality of empty cells withineach sheet. The method may include entering a filler entry into each ofthe plurality of cells determined to be empty.

The method may include copying each original sheet. The method may onlycopy a sheet that contains, in the first row of the sheet, apredetermined sequence of characters. In some embodiments, thepredetermined sequence of characters may be either “test name” or “testcase name”.

The method may include pasting each copied sheet into a single sheetwithin a monolithic spreadsheet. Each row included in each pasted sheetmay include a cell. The cell may include a file path of the sheet andspreadsheet from which the row was copied.

The method may include selecting a spreadsheet within the testingframework. The selected spreadsheet may be the monolithic spreadsheet.The method may include processing each test executable included in themonolithic spreadsheet. The method may include inserting the resultsfrom the processing of each test executable into a discrete cell withinthe row corresponding to the test executable. The cell may be located ina column designated for test executable results.

One or more rows may be included in the single sheet of the monolithicspreadsheet. The one or more rows may be separated into non-monolithic,preferably updated, spreadsheets. The separating may be based on thefile path of each row. Each row may be grouped together with other rowshaving a like file path.

The method may include transmitting the non-monolithic, updatedspreadsheets. The plurality of original spreadsheets may be receivedfrom a plurality of entities. Each non-monolithic, preferably updated,spreadsheet may be transmitted to an entity. The entity may be includedin the plurality of entities. The entity may be an entity from which therows included in the non-monolithic, updated spreadsheet originated.Each non-monolithic, updated spreadsheet may be transmitted to theentity from which it was received.

In some embodiments, the method may be compiled using Visual Basic(“VBA”) or any other suitable computing language.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the invention will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIGS. 1A and 1B show an illustrative spreadsheet according to certainembodiments;

FIGS. 2A and 2B show another illustrative spreadsheet according tocertain embodiments;

FIG. 3 shows an illustrative GUI (“Graphical user interface”) accordingto certain embodiments;

FIG. 4 shows another illustrative GUI in accordance with principles ofthe invention;

FIGS. 5A, 5B, 5C and 5D show an illustrative spreadsheet according tocertain embodiments;

FIGS. 6A and 6B show a prior art diagram; and

FIGS. 7A and 7B show an illustrative diagram according to certainembodiments.

DETAILED DESCRIPTION OF THE DISCLOSURE

An apparatus for consolidating test executables is provided. Theconsolidating may be for conserving computing resources duringprocessing of the test executables within a testing framework. Theapparatus may include a receiver. The receiver may be configured toreceive a plurality of spreadsheets. Each spreadsheet included in theplurality of spreadsheets may include at least one sheet. One row in aspreadsheet may be a test executable. Each row included in the at leastone sheet may include a test executable.

The apparatus may include a processor. The processor may be configuredto iterate through each sheet of each spreadsheet. When a sheet containsa predetermined text within at least one column header, the processormay retrieve all column headers included in the sheet. Iterating througheach sheet and retrieving column headers may enable the processor toretrieve preferably every relevant permutation of each possible testexecutable. Each sheet may comprise a plurality of test executables.Each test executable may comprise a plurality of test specifications.Each test specification may be included in a distinct column.

Each column may include a column header. Each column header may definethe contents of the test specifications included in the column. Bycombining all column headers, the processor may ensure that each testexecutable will be able to fit into the columns included in themonolithic spreadsheet. Because each test executable may not fill ineach column in the monolithic spreadsheet, the processor may insertfiller entries into the cells in included in a column corresponding to atesting specification that is not applicable to the specific testexecutable included in the row.

The processor may be configured to determine a unique set of retrievedcolumn headers. The processor may also be configured to copy each sheetfrom which the column headers were retrieved. The processor may notretrieve sheets that did not include the predetermined text in thecolumn header. This may be because some of the sheets included in thespreadsheets may not be test executable sheets. Therefore, there may belittle or no motivation to copy the sheets that do not include testexecutables into the monolithic spreadsheet.

In some embodiments, the processor may be configured to retrieve all ofthe column headers. Following the retrieval of all the column headers,the processor may then remove the duplicates. In other embodiments, theprocessor may only retrieve the unique column headers. The processor mayalso be configured to copy each sheet from which the column headers wereretrieved. The processor may also be configured to paste each copiedsheet into a single sheet of a monolithic spreadsheet. The processor mayalso be configured to determine at least one empty cell within eachsheet included in the plurality of spreadsheets. The processor may beconfigured to enter a filler entry into the at least one determinedempty cell.

The processor may be configured to place a cell in each row of eachpasted sheet that includes the file path and the sheet from which it wascopied. The processor may also be configured to select the monolithicspreadsheet in the testing framework.

In some embodiments, the selecting may be performed by a user. Theprocessor may be configured to process each test executable included inthe single sheet within the monolithic spreadsheet. The processing mayobtain a results set. The processor may be configured to insert theresults from the processing each test executable into a discrete cellcorresponding to the test executable. Each of the discrete cells may belocated within the monolithic spreadsheet. Each discrete cell may belocated in a column designated for test executable results. Eachdiscrete cell may be located in the row corresponding to the testexecutable with which it is associated.

One or more rows may be included in the monolithic spreadsheet. Theprocessor may be configured to separate the one or more rows intoindividual spreadsheets. The separation may be implemented based on thefile path located in each row. The rows may be grouped with other rowshaving a like file path.

A column header may correspond to one or more testing specifications.The testing specifications may correspond to a test included in thesheet from which it was copied. The receiver may receive a plurality ofspreadsheets from a plurality of entities. The apparatus may be compiledusing VBA (visual basic). Examples of testing specifications may be testidentification number, test case name, scenario identification number,business scenario, transaction name, base message, consumer line ofbusiness, transaction status, provider and event name.

The processor may also be configured to remove the filler entries. Theprocessor may also be configured to remove the cells comprising the filepath.

The apparatus may also include a transmitter. The transmitter may beconfigured to transmit the individual spreadsheets. The transmission mayoccur following the removal of the filler entries and following theremoval of the cells comprising the file path.

The transmitter may also be configured to transmit each individualspreadsheet to the entity from which the rows included in the individualspreadsheet originated.

A method for consolidating DDT (Data Driven Testing) spreadsheets foruse with a testing executable program is provided. The method mayinclude storing a plurality of DDT spreadsheets in a collective DDTfolder. The method may include creating a single collective spreadsheet.The method may also include storing the single collective spreadsheet inthe collective DDT folder. The method may also include determining aplurality of empty cells within each DDT spreadsheet. The method mayinclude entering a filler entry into each cell determined to be empty.

There may be two or more possibilities of when filler entries may beplaced in spreadsheets. The timing of the placement of the fillerentries may depend on the type of the original spreadsheet. When theoriginal spreadsheet is an individual type spreadsheet—i.e., aspreadsheet that only contains columns pertaining to the testexecutables contained within the spreadsheet—the filler entries may notbe entered until the individual spreadsheet is copied into a monolithicspreadsheet. When the original spreadsheet is a universal typespreadsheet—i.e., a spreadsheet that contains columns pertaining to alltypes of test executables—the filler entries may be entered into theoriginal spreadsheet or into the monolithic spreadsheet. In thisscenario, the filler entries may be entered into the originalspreadsheet because each row may contain empty cells that are associatedwith other types of test executables.

The following exemplary table is an example of an original spreadsheetof type “individual.” Test executable rows A, B and C may be included inan original spreadsheet of type “individual.” See Table A.

TABLE A Test Executable Name Test ID Base Message Business Scenario A1022 G2G_MR409 Positive B 2099 G3G_MR809 Negative C 4988 G1G_MR897Positive

The following exemplary table is an example of an original spreadsheetof type “universal.” Test executable rows D, E and F may be included inan original spreadsheet of type “universal.” See Table B.

TABLE B Test Executable Test Base Business Transaction Scenario Name IDMessage Scenario Name ID Consumer D 4566 AdminPayment 6744 GND E 8688ACH 9766 CUST F 8892 Check 6200 BAU

Table B shows a universal spreadsheet. Columns Base Message and BusinessScenario may be included in table B, even though they may beinapplicable for test executables D, E and F because table B is auniversal type spreadsheet.

The following exemplary table is an example of a monolithic spreadsheet.Table C shows table A and table B combined into a monolithicspreadsheet.

TABLE C Test Executable Test Base Business Transaction Scenario Name IDMessage Scenario Name ID Consumer A 1022 G2G_MR409 Positive B 2099G3G_MR869 Negative C 4988 G1G_MR897 Positive D 4566 AdminPayment 6744GND E 8688 ACH 9766 CUST F 8892 Check 6200 BAU

It should be appreciated that filler entries may be placed in themonolithic spreadsheet. It should also be appreciated that fillerentries may be placed in an original spreadsheet, prior to beingtransferred to a monolithic spreadsheet, in the event that the originalspreadsheet is of type universal, as shown in Table B. It may bedifficult to include filler entries in an original spreadsheet that isof type individual because the individual type spreadsheet may notinclude columns which are irrelevant to the test executables included inthe individual type spreadsheet.

The method may also include entering a filler entry into each celldetermined to be empty. The method may also include copying each sheetthat includes at least one test executable. Each sheet may be includedin a DDT spreadsheet. The copied sheets may be pasted into a singlecollective spreadsheet. The method may include processing each testexecutable included in the single collective spreadsheet. The method mayinclude placing the results of each test executable alongside the testexecutable. The method may include copying the test executables and thetest executable results into the plurality of DDT spreadsheets fromwhich the test executables were copied.

Apparatus and methods described herein are illustrative. Apparatus andmethods in accordance with this disclosure will now be described inconnection with the figures, which form a part hereof. The figures showillustrative features of apparatus and method steps in accordance withthe principles of this disclosure. It is to be understood that otherembodiments may be utilized and that structural, functional andprocedural modifications may be made without departing from the scopeand spirit of the present disclosure.

The steps of methods may be performed in an order other than the ordershown and/or described herein. Embodiments may omit steps shown and/ordescribed in connection with illustrative methods. Embodiments mayinclude steps that are neither shown nor described in connection withillustrative methods.

Illustrative method steps may be combined. For example, an illustrativemethod may include steps shown in connection with another illustrativemethod.

Apparatus may omit features shown and/or described in connection withillustrative apparatus. Embodiments may include features that areneither shown nor described in connection with the illustrativeapparatus. Features of illustrative apparatus may be combined. Forexample, an illustrative embodiment may include features shown inconnection with another illustrative embodiment.

FIGS. 1A and 1B show illustrative spreadsheet 102. Spreadsheet 102 mayinclude a plurality of test executables. Each test executable mayinclude numerous test specifications. Each column may designate spacefor a test specification.

Spreadsheet 102 may include column 104. Column 104 may be directed tothe test specification that identifies a “Sino.” A Sino may include asequence number of the relevant test executable included in thespreadsheet.

Spreadsheet 102 may include column 106. Column 106 may be directed tothe test specification that identifies a scenario identification number.The scenario identification number may be a scenario associated with thetest executable.

Spreadsheet 102 may also include column 108. Column 108 may be directedto the test specification that identifies a test identification number.The test identification number may be a number that identifies therelevant test. For example, row 102 identifies the test entitled“RPI_MT202 COV_AdminPay_IFW_Validation_SenderReference_SW20_Numeric_Pos19.”

Spreadsheet 102 may also include column 110. Column 110 may be directedto the test specification that identifies the name of the testexecutable.

Spreadsheet 102 may also include column 112. Column 112 may be directedto the test specification that identifies the name of a businessscenario. In some embodiments, a business scenario may be positive,negative or neutral.

Spreadsheet 102 may also include column 114. Column 114 may be directedto the test specification that identifies the name of the transactionassociated with the test executable. In some embodiments, the name ofthe transaction may be limited to a specific subset of names that areincluded in a list of transaction names. A list of transaction names mayinclude: administer in payment, debit, credit, change name, changeidentification number, delete, reverse previous transaction and/or anyother suitable transaction name.

Spreadsheet 102 may also include column 116. Column 116 may be directedto the test specification that identifies the base message of the testexecutable.

Spreadsheet 102 may also include column 118. Column 118 may be directedto the test specification that identifies the consumer of the testexecutable. In some embodiments, the consumer may be a line of businessassociated with the requester of the test executable. In otherembodiments, the consumer may be the name, or other identificationmeans, of the requester of the test executable.

Spreadsheet 102 may also include column 120. Column 120 may be directedto the test specification that identifies that transaction status of thetest executable. In some embodiments, the transaction status may besuccessful, unsuccessful or in process.

Row 122 may delineate an exemplary test executable. The Sino of theexemplary test executable may be one, as shown in column 104. Thescenario identification number of the test executable may be “Scenario1”, as shown in column 106. The test identification number of the testexecutable may be “0001” as shown in column 108. The test case name ofthe test executable may be “RPI_MT202COV_AdminPay_IFW_Validation_SenderReference_SW20_N umeric_Pos19” asshown in column 110. The business scenario of the test executable may bepositive as shown in column 112. The transaction name of the testexecutable may be “administer in payment” as shown in column 114. Thebase message of the test executable may be “G2G_MT202COV_INPUT_With” asshown in column 116. The consumer of the test executable may be GBS asshown in column 118. GBS may be an acronym for global banking solutions.GBS may be an LOB (line of business). In some embodiments, the consumerof the test executable may be the recipient or beneficiary of the testexecutable. The transaction status of the test executable may besuccess, as shown in column 120.

FIGS. 2A and 2B show illustrative spreadsheet 202. Spreadsheet 202 mayinclude a plurality of test executables. Each test executable may occupya row of spreadsheet 202. Columns 204, 206, 208, 210, 212, 214, 216, 218and 220 may be substantially similar to columns 104-120 in FIG. 1.

Spreadsheet 202 include column 222. Column 222 may be directed to thetest specification that identifies a provider/source of the transactionassociated with the test executable. The provider of the test executablemay be an LOB.

Spreadsheet 202 may also include column 224. Column 224 may be directedto the test specification that identifies an event of the testexecutable. The event of the test executable may be a transformedcanonical payment. The event of the test executable may be any othersuitable event.

Spreadsheet 202 may also include tabs 228, 230, 232, 234 and 236. Thesetabs may indicate which sheet of the spreadsheet is open. It should beappreciated that, in a monolithic spreadsheet, there is preferably onlyone tab and only one sheet.

FIG. 3 shows exemplary test executable program 302. Program 302 mayenable a user to select a file. Program 302 may include data entrysection 304. Data entry section 304 may enable a user to select aspreadsheet to process. Data entry section 304 may enable a user tolimit the processing of the spreadsheet to specific rows or columnswithin the spreadsheet. As shown at 306, a user may preferably onlyselect one sheet in the sheet selection box.

Test case explorer 308 may enable a user to view the test executablesincluded within the selected sheet. Tests 1-6, shown at 310, may beincluded in the selected sheet. Rows section 312 may enable a user tochoose all of the rows in the selected sheet or a range of rows (notshown). Rows section 312 may also enable a user to select multipleranges of rows. Column section 316 may enable a user to select one ormore columns. Show columns button 318 may enable a user to view thecolumns in the selected sheet in order to select the relevant columns.

In some embodiments, the user may select specific rows or specificcolumns in a spreadsheet. The test executable program may only run thetests on the selected rows and columns.

FIG. 4 shows screenshot 402. Screenshot 402 may show a user selecting aspreadsheet from browse window 404. The selected file name may beincluded in entry filed 406. A user may select open button 408 in orderto open or upload the desired spreadsheet.

FIGS. 5A, 5B, 5C and 5D show exemplary merged file spreadsheet 502.Exemplary merged file spreadsheet 502 may be a monolithic spreadsheet,as described above. Spreadsheet 502 may only contain one sheet, as shownat merged file sheet 504. Merged file sheet 504 may be a compilation ofa plurality of sheets included in a plurality of spreadsheets. A testexecutable program may have the capability to process the entirety ofspreadsheet 502 in one instantiation because all of the test executablesare included in one sheet.

It should be appreciated that the test executables, which have beenimported from other spreadsheets, may require a mechanism,post-execution, for being returned to their original spreadsheets.Therefore, the system may include a marking system. The marking systemmay assign each test executable, included in the spreadsheet, anoriginal DDT address. The original DDT address, shown at 506 of FIG. 5A,may include the original spreadsheet location of the test executableincluded in the cells located on the same row. The original sheet, shownat 508 of FIG. 5B, may include the original sheet location of the testexecutable included in the cells located on the same row. The originalrow, shown at 510 of FIG. 5B, may include the original row of the testexecutable included in the cells located on the same row.

Columns 512, 514 and 516, shown in FIG. 5B, may be substantially similarto columns 104, 106 and 108 described in connection with FIG. 1. Column518, shown in FIG. 5B, may include a test specification that identifiesthe name of the test executable.

Column 520, shown in FIG. 5C, may include a test specification thatidentifies an amount. The amount may be an input test specification ofthe test executable. Column 522, shown in FIG. 5C, may also include atest specification that identifies an identification number. Theidentification number may be an input test specification of the testexecutable. Column 524, shown in FIG. 5C, may include an output of thetest executable. The output information may only be visible orapplicable upon the completion of the test executable program processingof spreadsheet 502. Column 526, shown in FIG. 5C may include a DDT fullpath of the test executable.

Column 528, shown in FIG. 5D, may include a sheet name of a monolithicspreadsheet a spreadsheet that includes one single sheet that includes aplurality of test executables which may have been combined from aplurality of spreadsheets and sheets therein. Column 530, shown in FIG.5D, may include a test specification that identifies a base message ofthe test executable. Columns 532, 534, 536 and 538 d, shown in FIG. 5D,may include additional input test specifications of the test executable.

FIGS. 6A and 6B show a prior art example of running a test caseexecution tool. Test executables may be included in a plurality ofspreadsheets and a plurality of sheets therein, shown at 602, 604 and606 in FIG. 6A. A user may be required to process each sheet separatelyat test execution tool 608 in FIG. 6A. Drop down menu 610, shown in FIG.6A, shows that only one sheet from one spreadsheet can be processed bythe test execution tool. Dialog box 612, shown in FIG. 6B, shows theprocessing of the selected sheet. Upon completion of the execution, auser was conventionally required to manually select another sheet fromthe spreadsheet and repeat the process. The process repetition may beshown at selection dialog box 614 and execution dialog 616.

FIGS. 7A and 7B show an exemplary embodiment of a test executableconsolidator according to the invention. Sheets 702, 704 and 706 may beconsolidated into monolithic spreadsheet 708. In addition, the DDT fullpath, shown at 710, and sheet name, shown at 712, may be incorporated inspreadsheet 708. At test executable dialog box 714 only one sheet may beselectable, as shown at 716. The one sheet may be processed, as shown atdialog box 718. It should be appreciated that, upon completion ofprocessing, monolithic spreadsheet 708 may be divided into the originalsheets 702, 704 and 706. The division may be based on DDT full path 710and sheet name 712. It should also be appreciated that prior totransmission of the post-processing original spreadsheets, DDT full path710 and sheet name 712 may be deleted. Deleting DDT full path 710 andsheet name 712 may enable a spreadsheet transmitter to receive theprocessed sheets without any difference even though the sheets had beencombined into a monolithic sheet.

Thus, methods and apparatus for test executable consolidation have beenprovided. Persons skilled in the art will appreciate that the presentinvention can be practiced by other than the described embodiments,which are presented for purposes of illustration rather than oflimitation. The present invention is limited only by the claims thatfollow.

What is claimed is:
 1. A method for consolidating test executables, saidconsolidating for conserving computing resources during processing ofthe test executables within a testing framework, the method comprising:receiving a plurality of original spreadsheets, wherein each originalspreadsheet included in the plurality of original spreadsheets comprisesat least one sheet, wherein each row included in each at least one sheetcomprises a test executable; identifying a plurality of empty cellswithin each sheet; entering a filler entry into each of the plurality ofempty cells; copying each sheet, included in each of the plurality oforiginal spreadsheets, that contains, in the first row of the sheet, adesignated sequence of characters; pasting each copied sheet into asingle sheet within a monolithic spreadsheet, said monolithicspreadsheet comprising only a single sheet, wherein each row included ineach pasted sheet included a cell that comprises a file path of thesheet and spreadsheet from which the row was copied; selecting, usingthe testing framework, the monolithic spreadsheet; processing each testexecutable included in the single sheet; inserting the results from theprocessing of each test executable into a discrete cell within the rowcorresponding to the test executable, the cell being located in a columndesignated for test executable results; separating one or more rows intogroups of rows sharing a like file path, said one or more rows includedin the single sheet; storing each of said groups into one of a pluralityof non-monolithic, updated, spreadsheets, the separating beingimplemented based on the file path of each group; and transmitting eachof the non-monolithic, updated spreadsheets.
 2. The method of claim 1,wherein the plurality of original spreadsheets are received from aplurality of entities.
 3. The method of claim 2, wherein eachnon-monolithic updated spreadsheet is transmitted to an entity, includedin the plurality of entities, from which the rows included in thenon-monolithic, updated spreadsheets originated.
 4. The method of claim2, wherein each non-monolithic, updated spreadsheet is transmitted tothe entity from which it was received.
 5. The method of claim 1, whereinthe designated sequence of characters is either “test name” or “testcase name”.
 6. The method of claim 1, wherein the designated sequence ofcharacters includes the word “test.”
 7. The method of claim 1, whereinthe method is compiled using Visual Basic (“VBA”).
 8. An apparatus forconsolidating test executables, said consolidating for conservingcomputing resources during processing of the test executables within atesting framework, a spreadsheet comprising one or more sheets, theapparatus comprising: a receiver configured to: receive a plurality ofspreadsheets, wherein each spreadsheet included in the plurality ofspreadsheets comprises at least one sheet, wherein each row included inthe at least one sheet comprises a test executable; a processorconfigured to: iterate through each sheet of each spreadsheet and, whena sheet contains a predetermined text within at least one column headerof the sheet, retrieve all column headers included in the sheet;construct, based on the iteration, a unique set of retrieved columnheaders; copy each sheet from which each of the column headers wereretrieved; paste each copied sheet into a single sheet of a monolithicspreadsheet; determine at least one empty cell within the monolithicspreadsheet; enter a filler entry into the at least one determined emptycell; place a cell in each row of each pasted sheet, the cell whichincludes the file path and the sheet from which it was copied; selectthe monolithic spreadsheet in the testing framework; process each testexecutable included in the single sheet within the monolithicspreadsheet, said processing to obtain a result set, said result setcomprising a plurality of results; insert each of said results from theprocessing of each test executable into a discrete cell corresponding tothe test executable, each of said discrete cells located within themonolithic spreadsheet, said discrete cells located in a columndesignated for test executable results, each of said discrete cellslocated in the row corresponding to the test executable; and separateone or more of the rows into groups of rows, each group of rows sharinga like file path, and storing each of said groups into a plurality ofindividual spreadsheets, the separation being implemented based on thefile path of each group.
 9. The apparatus of claim 8, wherein the columnheader corresponds to a testing specification, said testingspecification corresponding to a test included in the sheet of thespreadsheet from which it was copied.
 10. The apparatus of claim 9,wherein the at least one empty cell is included in a column that isdesignated for a specific testing specification, said specific testingspecification being unrelated to the row in which the at least one emptycell is included.
 11. The apparatus of claim 8, wherein the receiverreceives the plurality of spreadsheets by a plurality of entities. 12.The apparatus of claim 8, wherein the apparatus is compiled using VisualBasic (“VBA”).
 13. The apparatus of claim 8, wherein the processor isfurther configured to: remove the filler entries; and remove the cellscomprising the file path.
 14. The apparatus of claim 13, wherein theapparatus further includes a transmitter, and the transmitter isconfigured to transmit, following the removal of the filler entries andthe removal of the cells comprising the file path, the individualspreadsheets.
 15. The apparatus of claim 14, wherein the transmitter isfurther configured to transmit each individual spreadsheet to the entityfrom which the rows included in the individual spreadsheet originated.16. A method for consolidating DDT (data driven testing) spreadsheets,said spreadsheets for testing with a test executable program, the methodcomprising: storing a plurality of DDT spreadsheets in a collective DDTfolder; creating a single collective spreadsheet; storing the singlecollective spreadsheet in the collective DDT folder; identifying aplurality of empty cells within each DDT spreadsheet; entering a fillerinto each cell determined to be empty; copying each sheet that includesat least one test executable, said each sheet included in each DDTspreadsheet, into the single collective spreadsheet; processing eachtest executable included in the single collective spreadsheet; placingthe results of each test executable in a column orthogonal to the testexecutable row; and copying each test executable and results of eachtest executable into the plurality of DDT spreadsheets from which thetest executables were copied.